Systems, Methods, and Computer Program Products For Generating A Normalized Assessment Of Instructors

ABSTRACT

Systems, methods, and computer program products for generating a normalized assessment of instructors include calculating a first relative value unit (RVU) score for didactic instruction provided by the instructor, calculating a second RVU score for at least one of online instruction, seminar instruction, laboratory instruction, and/or simulation instruction provided by the instructor, calculating a third RVU score for practical experience instruction provided by the instructor, generating a normalized score for the instructor based on the first RVU score, the second RVU score, and the third RVU score, and displaying the normalized score for the instructor, where the first, second, and third RVU scores are each time-normalized scores.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/116,070, filed Aug. 29, 2018, entitled Systems, Methods, And Computer Program Products For Generating A Normalized Assessment Of Instructors, which claims priority to U.S. provisional patent application 62/552,667, filed Aug. 31, 2017, entitled “Systems, Methods, And Computer Program Products For Generating A Normalized Assessment Of Instructors,” the disclosures of which are incorporated herein in their entireties by reference.

FIELD OF THE INVENTION

The invention relates to systems, methods, and computer program products, and more specifically to computer systems that can generate an automated assessment of instructors performing various types of educational encounters.

BACKGROUND

In academic environments, an assessment of an instructor can assist in determining both the competence of the instructor as well as the instructor's overall contribution to the academic program.

For example, in academic environments which utilize accreditation, the academic environment (e.g., a college or university) may be required to submit information related to the academic environment in order to achieve or maintain the accreditation. The submitted information may include data which assists the accreditation organization with determining whether the academic environment is achieving its education goals. The number of hours of instruction provided by the instructor may be a factor in determining whether the academic program is achieving its education goals. While hours spent in the classroom may be utilized as an objective factor in an instructor evaluation, often such coarse measures do not reflect the full contribution of the instructor to the academic program. For example, opportunities in which the instructor provides demonstrations and/or other types of non-traditional learning environments may be difficult to quantify.

SUMMARY

Various embodiments described herein provide methods, systems, and computer program products for generating normalized assessments of instructors.

According to some embodiments described herein, a system for generating a normalized assessment of an instructor includes a processor, a display coupled to the processor, and a memory coupled to the processor and storing computer readable program code that when executed by the processor causes the processor to perform operations including calculating a first relative value unit (RVU) score for didactic instruction provided by the instructor, calculating a second RVU score for at least one of online instruction, seminar instruction, laboratory instruction, and/or simulation instruction provided by the instructor, calculating a third RVU score for practical experience instruction provided by the instructor, generating a normalized score for the instructor based on the first RVU score, the second RVU score, and the third RVU score, and displaying, via a graphical interface on the display, the normalized score for the instructor, where the first, second, and third RVU scores are each time-normalized scores.

According to some embodiments described herein, a method for generating a normalized assessment of an instructor includes calculating a first relative value unit (RVU) score for didactic instruction provided by the instructor, calculating a second RVU score for at least one of online instruction, seminar instruction, laboratory instruction, and/or simulation instruction provided by the instructor, calculating a third RVU score for practical experience instruction provided by the instructor, generating a normalized score for the instructor based on the first RVU score, the second RVU score, and the third RVU score, and displaying the normalized score for the instructor, where the first, second, and third RVU scores are each time-normalized scores.

According to some embodiments described herein, a computer program product for operating an imaging system includes a non-transitory computer readable storage medium having computer readable program code embodied in the medium that when executed by a processor causes the processor to perform operations including calculating a first relative value unit (RVU) score for didactic instruction provided by an instructor, calculating a second RVU score for at least one of online instruction, seminar instruction, laboratory instruction, and/or simulation instruction provided by the instructor, calculating a third RVU score for practical experience instruction provided by the instructor, generating a normalized score for the instructor based on the first RVU score, the second RVU score, and the third RVU score, and displaying the normalized score for the instructor, where the first, second, and third RVU scores are each time-normalized scores, where the first, second, and third RVU scores are each time-normalized scores.

In some embodiments, the didactic instruction comprises one or more encounters in which the instructor communicates directly to a plurality of students.

In some embodiments, the online instruction comprises one or more encounters in which a computer is a mechanism for delivery of content to a plurality of students, the seminar instruction comprises one or more encounters in which the seminar instruction guides discussions between one or more experts and the plurality of students, the laboratory instruction comprises one or more encounters that places a student of the plurality of students into the role of performing one or more tasks of a skill that augment an understanding of didactic knowledge of the skill, and the laboratory instruction comprises one or more encounters that places a student of the plurality of students into the role of performing one or more tasks of a skill that augment an understanding of didactic knowledge of the skill.

In some embodiments, the practical experience instruction comprises one or more encounters in which a student performs one or more tasks of a skill on a human patient under conditions corresponding to conditions experienced by those employed to perform the skill.

In some embodiments, the second and third RVU scores are based on a pre-defined assessment of difficulty and an estimated time for a student to complete a respective experiential task.

In some embodiments, calculating the first RVU score for the didactic instruction provided by the instructor includes defining learning objectives for respective ones of a plurality of didactic encounters, associating the learning objectives of the respective ones of the plurality of the didactic encounters with RVU quantities, and summing the RVU quantities for the plurality of the didactic encounters to determine the first RVU score.

In some embodiments calculating the second RVU score for at least one of the online instruction, the seminar instruction, the laboratory instruction, and/or the simulation instruction provided by the instructor includes assigning a percentage credit for the instructor in respective ones of a plurality of online, seminar, laboratory, and/or simulation encounters, defining learning objectives for the respective ones of the plurality of the online, seminar, laboratory, and/or simulation encounters, associating the learning objectives of the respective ones of the plurality of the online, seminar, laboratory, and/or simulation encounters with RVU quantities, for each of the plurality of the online, seminar, laboratory, and/or simulation encounters, determining an allocated RVU quantity for the instructor based on the associated RVU quantities for the learning objectives of the online, seminar, laboratory, and/or simulation encounter and the assigned percentage credit for the instructor in the online, seminar, laboratory, and/or simulation encounter, and summing the allocated RVU quantities for the instructor for respective ones of the plurality of the online, seminar, laboratory, and/or simulation encounters to determine the second RVU score.

In some embodiments, calculating the third RVU score for the practical experience instruction provided by the instructor includes providing input for qualitative assessment data for respective ones of a plurality of practical experience encounters in which the instructor participates, calculating practical experience RVUs for the respective ones of the plurality of the practical experience encounters based on the qualitative assessment data, and summing the practical experience RVUs for the plurality of the practical experience encounters to determine the third RVU score. In some embodiments, the qualitative assessment data for the respective ones the plurality of the practical experience encounters includes one or more learning objectives associated with at least one skill performed during the practical experience encounter and RVU values assigned to respective ones of the learning objectives. Calculating practical experience RVUs for the respective ones of the plurality of the practical experience encounters based on the qualitative assessment data may include calculating, for each skill of the at least one skill performed during the practical experience encounter, a per-skill RVU value based on a product of a number of students that performed the skill times the RVUs assigned to the one or more learning objectives associated with the skill, calculating a sum of the per-skill RVU values, and dividing the sum of the per-skill RVU values by a total number of the students that participated in the practical experience encounter to determine the practical experience RVUs for the practical experience encounter.

In some embodiments, the instructor is a first instructor of a plurality of instructors, and the methods, systems, and computer program products further include calculating the normalized score for each instructor of the plurality of instructors, generating a normalized report comprising the normalized score for each instructor of the plurality of instructors, and transmitting the normalized report as part of an accreditation process for an educational institution. In some embodiments, the normalized report further includes the first RVU score, the second RVU score, and the third RVU score for each instructor of the plurality of instructors. In some embodiments, the first RVU score, the second RVU score, and the third RVU score for each instructor include subtotals based on learning objectives, and the normalized report further comprises the subtotals based on the learning objectives for each of the first RVU score, the second RVU score, and the third RVU score.

It is noted that aspects of the inventive concepts described with respect to one embodiment, may be incorporated in a different embodiment although not specifically described relative thereto. That is, all embodiments and/or features of any embodiment can be combined in any way and/or combination. Other operations according to any of the embodiments described herein may also be performed. These and other aspects of the inventive concepts are described in detail in the specification set forth below.

BRIEF DESCRIPTION OF THE FIGURES

The above and other objects and features will become apparent from the following description with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.

FIG. 1 is a flowchart that illustrates example operations in a method for generating a normalized assessment of an instructor, according to various embodiments described herein.

FIG. 2 is a flowchart that illustrates example operations in a method for calculating academic credit for a didactic encounter associated with didactic instruction, according to various embodiments described herein.

FIG. 3 is an example of a user interface for the creation of a record for a didactic encounter, according to various embodiments described herein.

FIG. 4 is an example of a user interface for the creation of an example record that maps learning objectives for a didactic encounter, according to various embodiments as described herein.

FIG. 5 is an example of a user interface displaying a didactic encounter record with a plurality of learning objectives defined for the didactic encounter, according to various embodiments as described herein.

FIG. 6 is a flowchart that illustrates example operations in a method for calculating academic credit for a simulation encounter associated with simulation instruction, according to various embodiments described herein.

FIG. 7 is an example of a user interface for the creation of a record for a simulation encounter, according to various embodiments described herein.

FIG. 8 is an example of a user interface for allocating and/or editing a faculty credit percentage for a simulation encounter, according to various embodiments described herein.

FIG. 9 is an example of a user interface displaying a simulation encounter record with at least one learning objective defined for the simulation encounter, according to various embodiments as described herein.

FIG. 10 is an example of a user interface displaying an example report of an allocation of the simulation encounter of FIG. 9, according to various embodiments as described herein.

FIG. 11 is a flowchart that illustrates example operations in a method for calculating academic credit for a practical experience encounter associated with practical experience instruction, according to various embodiments described herein.

FIG. 12 is an example of a user interface for the creation of a record for a practical experience encounter, according to various embodiments described herein.

FIG. 13 is an example of a user interface displaying an example set of quantitative assessment data for an example set of practical experiences, according to various embodiments as described herein.

FIG. 14 is an example of a user interface presenting an example allocation of RVUs for instructors for a practical experience encounter (clinical session) with multiple microcompetencies, according to various embodiments as described herein.

FIGS. 15-19 are example user interfaces displaying examples of aggregation reports that can be generated from the collected data, according to various embodiments as described herein.

FIG. 20 is a block diagram of an assessment system, according to various embodiments as described herein.

DETAILED DESCRIPTION

The present invention will now be described more fully hereinafter with reference to the accompanying figures, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Like numbers refer to like elements throughout.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. As used herein, phrases such as “between X and Y” and “between about X and Y” should be interpreted to include X and Y. As used herein, phrases such as “between about X and Y” mean “between about X and about Y,” As used herein, phrases such as “from about X to Y” mean “from about X to about Y.”

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the specification and relevant art and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Well-known functions or constructions may not be described in detail for brevity and/or clarity.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, components, regions, features, steps, layers and/or sections, these elements, components, features, steps, regions, layers and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, feature, step, region, layer or section from another region, layer or section. Thus, a first element, component, region, layer, feature, step or section discussed below could be termed a second element, component, region, layer, feature, step or section without departing from the teachings of the present invention. The sequence of operations (or steps) is not limited to the order presented in the claims or figures unless specifically indicated otherwise.

As will be appreciated by one skilled in the art, aspects of the present invention may be illustrated and described herein in any new and useful process, machine, manufacture, or composition of matter, and/or any new and useful improvement thereof. Accordingly, aspects of the present invention may be implemented entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or combining software and hardware implementations that may all generally be referred to herein as a “circuit,” “module,” “component,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.

Any combination of one or more computer readable media may be utilized. The computer readable media may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a Software as a Service (SaaS).

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable instruction execution apparatus, create a mechanism for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that when executed can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions when stored in the computer readable medium produce an article of manufacture including instructions which when executed, cause a computer to implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable instruction execution apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatuses or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The term “(curriculum) encounter” refers to an education experience and/or encounter that involves instructors and a cohort of students.

The term “didactic (type) encounter” refers to an encounter where an instructor communicates to a group that is to be instructed (e.g., students in a class). Video recordings of presentations may fall in this category. Didactic instruction refers to one or more of such didactic encounters. The didactic encounter can be associated with a single instructor.

The term “online (type) encounter” refers to an encounter where a computer (e.g., via intranet or intranet) is the mechanism for delivery of content to students. An online encounter may differ from asynchronous delivery of a presentation in that the online encounter may involve direct navigation by a respective student using a computer. Multiple instructors may be involved in the instruction of an online (type) encounter to subsets of the class, the entire class, and/or subsets of students of more than one class on the same topics. Online instruction refers to one or more of such online encounters.

The term “seminar (type) encounter” refers to an encounter that primarily involves guided discussions between experts/teachers and students. This may include a multitude of interactive techniques including, for example, flipped class room, case-based learning, and/or problem-based learning. Multiple instructors may be involved in the seminar encounter to subsets of the class, the entire class, and/or subsets of students of more than one class on the same topics. Seminar instruction refers to one or more of such seminar encounters.

Program training on laboratory sciences can include simulation encounters, laboratory encounters, and/or practical experience encounters. The term “simulation (type) encounter” refers to an encounter that places the student into a role of performing a task or tasks that approximate an actual work or skill that will be performed by the graduate of the program during their job or profession. For medical disciplines, this may involve, for example, performing surgeries on simulated patients. Multiple instructors may be involved in the simulation encounter to subsets of the class or the entire class on the same topics. Simulation instruction refers to one or more of such simulation encounters.

The term “laboratory (type) encounter” refers to an encounter that places the student into a role of performing a task or tasks that augment the understanding of didactic knowledge. Multiple instructors may be involved in the laboratory encounter to subsets of the class or the entire class on the same topics. Laboratory instruction refers to one or more of such laboratory encounters.

The term “practical experience (type) encounter” refers to an encounter where the student performs the actual task or tasks that they will be performing in the same or similar conditions as they will perform them following graduation in their job or profession. In medical disciplines, for example, this may include performing surgery on actual patients. Practical Experience instruction refers to one or more of such practical experience encounters.

The term “microcompetency code” refers to a detailed code for assigning topics to encounters for mapping to program competencies. There may be four levels of hierarchy—(1) Discipline, (2) Topic, (3) Subtopic, and (4) Microcompetency Code. An example is as follows:

Discipline: 2604—Cellular Biology and Anatomical Sciences

Topic: 2604.009—Gross Anatomy (Human)

Subtopic: 2604.009.200—Skeleton Gross Anatomy

Microcompetency: 2604.009.200.210—Cervical Vertebrae

The term “program (curriculum) competency” refers to a set of topics that are tracked across all courses of a program to be encountered and successfully assessed to reach “competence” as a predictor of performing well following graduation. From a viewpoint of encounter mapping, a single competency can include a single micro competency, but, in some embodiments, may include many microcompetency codes. An example is as follows:

-   -   Competency SoDM20—Patient Assessment     -   Microcompetency: 5104.150.000.000—Dental Diagnostic Sciences,         General     -   Microcompetency: 5104.150.100.100—Microbiology Cultures and         Tests, General     -   Microcompetency: 5104.150.100.200—Genetic Tests, General     -   Microcompetency: 5104.150.100.300—Salivary Tests, General     -   Microcompetency: 5104.150.100.400—Tissue Examinations, General     -   Microcompetency: 5104.150.200.000—Dental Clinical Examinations         and Tests, General     -   Microcompetency: 5104.150.200.100—Patient Screening, General     -   Microcompetency: 5104.150.200.200—Limited Examination, General     -   Microcompetency: 5104.150.200.210—Caries Susceptibility         Examination, General     -   Microcompetency: 5104.150.200.220—Pulp Vitality Examination,         General     -   Microcompetency: 5104.150.200.300—Comprehensive Examination,         General     -   Microcompetency: 5104.150.200.400—Case Re-examination/Outcomes         Assessment, General     -   Microcompetency: 5104.150.300.000—Dental Diagnostic Casts and         Models, General     -   Microcompetency: 5104.150.300.100—Diagnostic Waxup, General     -   Microcompetency: 5104.150.400.200—Intraoral Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.000—Oral Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.210—Periapical Radiographic         Examination, General     -   Microcompetency: 5104.150.400.220—Bitewing Radiographic         Examination, General     -   Microcompetency: 5104.150.400.230—Occlusal Radiographic         Examination, General     -   Microcompetency: 5104.150.500.000—Oral Photographic         Examinations, General     -   Microcompetency: 5104.150.400.100—Extraoral Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.110—Panoramic Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.120—Skull/Cephalometric         Radiographic Examinations, General     -   Microcompetency: 5104.150.400.130—Tomographic Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.140—Sialographic Radiographic         Examinations, General     -   Microcompetency: 5104.150.400.150—Temporomandibular Joint         Radiographic Examinations, General     -   Microcompetency: 5104.150.400.160—Ultrasound Radiographic         Examinations, General

The term “relative (educational) value unit” (RVU or ReVU) refers to a point system based on a common heuristic across all encounter and assessment types. While the basis of relative value can be based on anything, in some embodiments, the basis is time. When normalizing an encounter, mapping time of the encounter may be defined. As an example, in some embodiments, 15 minutes may be equal to 1 point. Alternatively, in some embodiments, 60 minutes may be equal to 1 point. By assigning points to time, the data from the encounter maps can be compared to assessment points. Relative value units are described in commonly assigned U.S. patent application Ser. No. 13/425,627, filed on Mar. 21, 2012, the contents of which are incorporated herein by reference. In some embodiments, some RVUs may be based on a pre-defined assessment of difficulty and an estimated time to complete a respective experiential task.

The term “cohort” refers to a set of students who begin an educational program at the same time (e.g., same semester, term, or academic year). While graduation date/year may be implied by the start date, some students drop out of the program early or fail components and graduate late. Cohort evaluation is useful for program analysis because it may be used to look at the achievement of multiple students encountering the same instruction. Cohort analysis may follow the same student and/or cohort across multiple academic years. Cross-cohort analysis may allow for encounter analysis for multiple cohorts.

The term “academic year” refers to the program-defined start and finish of academic activity. For example, a program may begin in the Fall Term and end at the end of the Summer Term(s). Academic year evaluation is useful for program analysis because it may be used to look at faculty performance while instructing students in multiple cohorts that happen during the same time span. Cross-academic year analysis may allow for encounter analysis for multiple years.

The present invention utilizes systems, methods, and computer program products to provide academic credit to instructors across a wide range of educational encounter types. The comparisons described herein also allow for the normalization across the various types of encounters to provide an objective means of comparison across a plurality of instructors. These methods, systems, and computer program products described herein promote technical efficiency within the review process. For example, objective means of determining academic credit may allow for automation of the generation of accreditation reports. Because the credit may be easily quantified and compared, the generation of reports required for accreditation may be performed with minimum human input. This may allow for a repeatable process that reduces errors, improves efficiency, minimizes and/or reduces resources required for accreditation, and improves transparency in instructor evaluation. Such methods, systems, and computer program products provide a reduction in technical and personnel resources required for instructor evaluation. In addition, the methods, systems, and computer program products described herein provide an improved technical process to accomplish accreditation for an educational institution. For example, the accreditation of schools, programs, colleges, and universities relies on accurate curriculum mapping data. In the past, educational programs primarily relied solely on the number of lectures to provide curriculum information, but competency-based education emphasizes that all types of instruction be properly mapped. Such a mapping is technically difficult to achieve in a conventional environment. The techniques described herein allow for real-time analysis of the effects of instruction change on student performance, and can automatically provide the data used for accreditation. Thus, the methods, systems, and computer program products described here are not only more efficient than conventional means of curriculum reporting, but they also provide a level of accuracy in the reporting that was not previously available.

FIG. 1 illustrates a method for generating a normalized assessment of an instructor, according to various embodiments described herein. As illustrated in FIG. 1, a method for generating a normalized assessment of an instructor may include calculating credit for didactic instruction (block 100), calculating credit for online, seminar, laboratory, and/or simulation instruction (block 2000, calculating credit for practical experience instruction (block 300), and generating aggregation reports associated with the calculated credits (block 400). Though the method describes multiple types of education encounters, it will be understood that not all assessments will involve each type of encounter. For example, some assessments may include online encounters, but not laboratory or simulation. Similarly, some assessments may include reviews of didactic instruction and practical experiences, but not online, seminar, laboratory, and/or simulation instruction. Various combinations of educational encounters may be combined, included, or excluded from the present methods, systems, and compute program products without deviating from the present invention.

Calculating Credit for Didactic Instruction (Lecture)

Methods, systems, and compute program products according to the present invention may include calculating credit for didactic instruction (block 100, FIGS. 1 and 2). Calculating credit for didactic instruction may include calculating credit for one or more didactic encounters. FIG. 2 illustrates a method for calculating academic credit for a didactic encounter associated with didactic instruction, according to various embodiments described herein. As illustrated in FIG. 2, giving credit for a didactic encounter may include additional sub-operations (blocks 110, 120, 130), as described further herein.

Creating the Didactic Encounter with Rules

A didactic encounter may be created with reference to particular mapping rules. In some embodiments, a user interface of an electronic device may be used to create a record for the didactic encounter (FIG. 2, block 110). The didactic encounter may be the normalization reference standard for encounter mapping. For example, in some embodiments, instruction performed in other types of encounters (e.g., online, laboratory, etc.) may be compared to an equivalent level of instruction in a didactic encounter.

A didactic encounter may be created based on a number of rules. First, the encounter may happen at a specific date and time. Second, during a didactic encounter, one instructor may speak about a single topic at a time for a defined amount of time. In some embodiments, it is possible for more than one instructor to lecture during the same encounter. However, in a lecture, one instructor may speak at a time to the entire class. The details of the participating instructor may be managed by the mapping of learning objectives. FIG. 3 illustrates an example of a user interface 390 for the creation of a record for a didactic encounter, according to various embodiments described herein. As illustrated in FIG. 3, a particular number of RVUs may be assigned to the didactic encounter based on the duration of the didactic encounter. For example, if one RVU corresponds to an equivalent of 15 minutes of instruction, a one hour didactic encounter may be assigned four RVUs.

Defining the Learning Objectives

Learning objectives may be defined with respect to the didactic encounter (FIG. 2, block 120). In some embodiments, the learning objectives may be associated with the record created on an electronic device in block 110. Again, for a didactic encounter the learning objective may be directly assigned to a single (identified) instructor. The mapping may be done directly in the learning objective. FIG. 4 illustrates an example of a user interface 490 for the creation of an example mapping for learning objectives a didactic encounter, according to various embodiments as described herein. As illustrated in FIG. 4, the learning objective may be defined (e.g., “Discuss organization and structure of human genome”) and numbered. In some embodiments, the learning objective may be connected to a Microcompetency Code. The estimated amount of time may be translated to a RVU (e.g., 15 minutes equals 1 RVU). Finally, the faculty member may be associated with the learning objective.

Associating the Learning Objectives with the Didactic Encounter

The learning objectives for a particular didactic encounter may be generated to define all of the learning objectives available for the didactic encounter (FIG. 2, block 130). FIG. 5 illustrates an example of a user interface 590 displaying a didactic encounter record with a plurality of learning objectives defined for the didactic encounter, according to various embodiments as described herein. As illustrated in FIG. 5, an example one hour lecture may cover four different topics by the same instructor for 15 minutes for each topic. Accordingly, as illustrated in the example, each topic may receive one RVU allocation. Again, it is possible that more than one instructor lectures in the same hour. However, in some embodiments, the didactic encounter may be defined by each instructor speaking to the entire class individually.

For a given didactic encounter, calculating the credit provided to the instructor for a given didactic encounter may involve the summation of the RVUs associated with each learning objective of the didactic encounter. Calculating the credit provided to the instructor for didactic instruction may involve summing the credit provided for each of the didactic encounters in which the instructor participates.

Calculating Credit for Online, Seminar, Laboratory, and/or Simulation Instruction

Referring back to FIG. 1 (in block 200) methods, systems, and computer program products according to the present invention may include calculating credit for online, seminar, laboratory, and/or simulation instruction. From a curriculum mapping perspective, the online, seminar, laboratory and simulation encounters may each be mapped in a same or similar way even though the nature of the encounters are different. In these four encounter types, there may be more than one instructor working with the students at the same time. This differs from some types of didactic instruction (e.g., a lecture) where only one instructor may work with the entire class at a time. For example purposes, the simulation encounter will be used as a representative example for the online, seminar, laboratory, and simulation encounters described herein. However, it will be understood by those of skill in the art that the method used for the simulation encounter type may also be used for the online, laboratory, and/or simulation encounter types similarly. Calculating credit for simulation instruction may include calculating credit for one or more simulation encounters. FIG. 6 illustrates a method for calculating academic credit for an online, laboratory, and/or simulation encounter associated with online, laboratory, and/or simulation instruction, according to various embodiments described herein. As illustrated in FIG. 6, calculating academic credit for the simulation encounter may include additional sub-operations (blocks 210, 220, 230, and 240), as described further herein.

Creating Simulation Encounter

A record of the simulation encounter may be created (FIG. 6, block 210). In a similar manner as was described with respect to the didactic encounter, the simulation encounter may be numbered and described with its date range. There are at least three differences between the simulation type encounter and the didactic type encounter. First, with the simulation type encounter, a Faculty Group may define all of the instructors involved. Second, a Faculty Lead may identify the instructor who leads the simulation encounter. Third, a Faculty Lead Credits Percentage may define the percentage (out of 100) that is credited to the Faculty Lead for their work that is over and above the others in the Faculty Group for leading the simulation encounter. By making the Faculty Lead Credits Percentage equal to 0, it is the same as making all instructors equal. FIG. 7 illustrates an example of a user interface 790 for the creation of a record for a simulation encounter, according to various embodiments described herein.

In some embodiments, it may be possible for the Faculty Lead to create the simulation encounter and not participate in the simulation encounter itself. In such an embodiment, the Faculty Group may not include the Faculty Lead. This may mean that the Faculty Lead receives credit only for the percentage in the Faculty Lead Credits Percentage but would not split the RVUs from the group.

Assigning Faculty Credits Percentage

A credit percentage for the educational encounter may be assigned to the faculty members involved (FIG. 6, block 220). FIG. 8 illustrates an example of a user interface 890 for the allocating and/or editing a faculty credit percentage for a simulation encounter, according to various embodiments described herein. In FIG. 8, an example allocation is made for a simulation encounter related to “scaling and root planing.” As illustrated in the example of FIG. 8, there are two instructors in this simulation encounter, and one (Instructor 2) has been assigned as the Faculty Lead. The Faculty Lead is given 20% credit as lead, leaving 80 percent to the RVUs to be split equally between both instructors (Instructors 1 and 2). Since the encounter only includes one other instructor (Instructor 1), the instructor performing the Faculty Lead role (Instructor 2) gets the 20% credit as lead, plus one half of the remaining credit, for a total of 60% (20% plus 40%). The other instructor (Instructor 1) would receive 40%.

Creating Simulation Learning Objectives

The learning objectives of the simulation may be created and assigned to the encounter (FIG. 6, block 230). FIG. 9 illustrates an example of a user interface 990 displaying a simulation encounter record with at least one learning objective defined for the simulation encounter, according to various embodiments as described herein. Though FIG. 9 illustrates only a single objective, the present invention is not limited thereto. Similarly to the didactic encounter, the learning objective(s) may be created with microcompetencies and RVUs. One difference between the didactic encounter and the simulation is that the simulator assignments are assigned to the encounter and not the individual instructor. As illustrated in FIG. 9, there is only one learning objective with one microcompetency and 16 RVUs to be divided based on the rules of the encounter as previously defined (FIG. 6, block 220).

Assigning Credit Based on Rules of the Encounter:

The credit from the simulation encounter may be respectively assigned to the participating faculty (FIG. 6, block 240). In some embodiments, this allocation may occur after the educational encounter is complete, though the present invention is not limited thereto. FIG. 10 illustrates an example of a user interface 1090 displaying an example report of an allocation of the simulation encounter of FIG. 9, according to various embodiments as described herein. As illustrated in FIG. 10, from the rules of the simulation encounter, 20% of the 16 RVUs are automatically assigned to the lead instructor, and then the remaining 80% is split equally. This yields a reporting of 60% of the RVUs from the encounter (9.6 RVUs) to the Faculty Lead (Instructor 2) and the remaining 40% (6.4 RVUs) to the other faculty member in the group (Instructor 1).

For a given simulation encounter, calculating the credit provided to the instructor may involve the summation of the RVUs associated with each learning objective of the simulation encounter as allocated based on the rules of the simulation encounter. Calculating the credit provided to the instructor for simulation instruction may involve summing the credit provided for each of the simulation encounters in which the instructor participates.

Calculating Credit for Practical Experience Instruction

Methods, systems, and computer program products according to the present invention may include calculating credit for practical experience instruction (FIG. 1, block 300). Calculating credit for practical experience instruction may include calculating credit for one or more practical experience encounters. FIG. 11 illustrates a method for calculating academic credit for a practical experience encounter associated with practical experience instruction, according to various embodiments described herein. As illustrated in FIG. 11, giving credit for the practical experience encounter type may include additional sub-operations (blocks 310, 320, 330), as described further herein.

Creating Practical Experience Encounter

To give credit for a given practical experience encounter, a record of the practical experience encounter may be created (FIG. 11, block 310). Practical Experiences are encounters where the student performs, in front of an appropriate expert, the task or tasks that the student will perform as part of their job or profession after he or she graduates. In the case of some practical experiences, this performance may educationally happen over a period of time (e.g., a week or month), different students may be assigned to different faculty graders at different times over the span of the entire assessment, and the students may be performing very different tasks in different quantities. Practical experiences may be difficult to quantify because the variables are numerous. The present invention mathematically connects the student assessments that are evaluated by the faculty to the curriculum map.

In some embodiments, the base standard for curriculum mapping is the lecture (e.g., a didactic encounter), which may involve an instructor talking to all students in the course about a topic for a certain amount of time. In such an encounter, one instructor may get the entire credit (e.g., 1 RVU) for lecturing for 15 minutes to everyone in the class. For the Practical Experience encounter, different students may be performing different procedures for different amounts of time.

If focus is given to the assessment of a student's participation in practical experiences, three steps may be performed. First, all of the performed procedures may be assigned microcompetency codes and RVUs. Second, all of the coded procedures may be aggregated for all students over the time span that is evaluated. Third, the instructor who validated that the procedures were completed is identified for each student experience. This is called a Quantitative Skills Assessment, meaning that this is an assessment of the number of points generated for successfully completing a procedure. Note that there can be qualitative modifiers for the RVUs, but that may be a secondary process. FIG. 12 illustrates an example of a user interface 1290 for the creation of a record for a practical experience encounter, according to various embodiments described herein. As illustrated in FIG. 12, the faculty credit for the completed procedures may be directly connected to the Quantitative Skills Assessment of the student. The user interface illustrated in FIG. 12 may link the practical experience of the student directly to the related Quantitative Skills Assessment. There are different types of educational encounters that may take their data directly from an assessment. Examples of these are practical experience from a Quantitative Skills Assessment, and seminar experience that may take its data from a Discussion Assessment. Since the students may all have different experiences, different students may learn different things from different faculty members, in contrast to an educational experience in which every student learns the same thing from the same faculty. The assessments such as those illustrated in FIG. 12 record which faculty members teach what things to which students. This may allow for the creation of “learning objectives” from the recorded assessments.

Inputting the Quantitative Assessment Data

Referring back to FIG. 11, the quantitative assessment data for a given practical experience encounter may be entered and associated with the practical experience record (FIG. 11, block 320). Each procedure may be itemized with the date, student, faculty, microcompetency code, and/or RVUs. FIG. 13 illustrates an example of a user interface 1390 displaying an example set of quantitative assessment data for an example set of practical experiences, according to various embodiments as described herein. As illustrated in FIG. 13, the quantitative assessment data may include the student 1310 performing the task, the instructor 1320 overseeing the task, a microcompetency code 1340 associated with the task, and a number of RVUs 1350 associated with the task. In some embodiments, a tieback ID 1330 may be included. The tieback ID may 1330 indicate a particular or session (e.g. a practical experience encounter) in which the task was completed.

Mathematically Calculating the Faculty Credit

Referring back to FIG. 11, faculty credit may be assigned based on analysis of the completed practical experience quantitative assessment data and the associated faculty (FIG. 11, block 330). This operation may involve two steps. First, for a given instructor, all RVUs for each microcompetency code for each student may be summed for the date range of the assessment. Second, the total RVUs may be divided by the total number of students in the cohort to normalize the number of points for the entire cohort. In some embodiments, there may be a minimum of 0.1 RVUs allocated even if the number of RVUs/students value is a smaller number.

For example, if a given instructor worked with three students out of a cohort of 10 on a single microcompetency code worth 10 RVUs, the instructor would be given credit for 3 RVUs ((10 RVUs*3 students)/10 students in the cohort). FIG. 14 illustrates a user interface 1490 presenting an example allocation of RVUs for instructors for a practical experience encounter (clinical session) with multiple microcompetencies, according to various embodiments as described herein.

Generating Aggregation Reports

Methods, systems, and computer program products according to the present invention may include creating aggregation reports based on the collected data from the various educational encounters (FIG. 1, block 400). FIGS. 15-19 illustrate examples of a user interface displaying example aggregation reports that can be generated from the collected data, according to various embodiments as described herein.

For simplicity sake only, the provided examples only illustrate data associated with practical experiences. However, these same reports may similarly display the RVUs for all faculty members for all encounter types. In some embodiments, the granularity of reports may be related to the curricular level. Higher granularity may occur closest to the actual encounter. The encounters may happen within courses, so the course reports may have a higher granularity. Cohort reports may combine the results from all courses given to a cohort over the multiple years of the cohort's matriculation. Academic Year reports may combine the results across all courses within a calendar academic year. Cross-Cohort reports may compare results for cohorts over time for program analysis. Cross-Academic Year reports may compare results for years over time for program analysis.

Course/Section Encounter Reports

FIG. 15 illustrates an example course/section encounter report 1595. The course encounter reports may aggregate the RVUs for a given course and/or section and map them by the sub-topic of the microcompetency for each instructor. This report may rank the instructors by total RVUs, and may total all RVUs for the course, yielding a percentage participation for each participating faculty member. The left column of the example report is grouped by instructor 1510, with a given code provided for each instructor to protect anonymity. For each instructor, totals for respective types of educational encounters are shown, with a breakdown by topic codes 1520. Though topic codes 1520 are illustrated in FIG. 15, it will be understood that other types of reports (e.g., subtopic-based, microcompetency-based) may be generated without deviating from the present invention. The example report 1595 provided in FIG. 15 may be only a portion of the final aggregated report.

Cohort Encounter Reports

FIG. 16 illustrates an example cohort report 1695. The cohort report may aggregate the encounter RVUs for each instructor for all courses and may map them by topic of the microcompetency for all years of a specific cohort. The cohort report may total all RVUs and may yield a percentage participation for each instructor for program analysis. As in the prior example, the left column of the example report is grouped by instructor 1550, with a given code provided for each instructor to protect anonymity. For each instructor, totals for respective types of educational encounters are shown across the cohort, with a breakdown by topic codes 1560. Though topic codes 1560 are illustrated in FIG. 16, it will be understood that other types of reports (e.g., subtopic-based, microcompetency-based) may be generated without deviating from the present invention. The example report 1695 provided in FIG. 16 may be only a portion of the final aggregated report.

Academic Year Encounter Reports

FIG. 17 illustrates an example academic year report 1795. The academic year report may aggregate the encounter RVUs for each instructor for all courses and maps them by topic of the microcompetency for all cohorts during a single academic year. The academic year report may total all RVUs and yield a percentage participation for each instructor for program analysis. As in the prior example, the left column of the example report is grouped by instructor 1710, with a given code provided for each instructor to protect anonymity. For each instructor, totals for respective types of educational encounters are shown across the cohort, with a breakdown by topic codes 1720. Though topic codes 1720 are illustrated in FIG. 17, it will be understood that other types of reports (e.g., subtopic-based, microcompetency-based) may be generated without deviating from the present invention. The example report 1795 provided in FIG. 17 may be only a portion of the final aggregated report.

In some embodiments, cross-cohort and cross-academic year reports may be distinguished because they are specific to the programs and are defined by their competencies. A competency is a collection of micro competencies that define the ways that the program wants to evaluate success. The competency may be a different metric than the higher-level topics and subtopics.

Cross-Cohort Encounter Reports

FIG. 18 illustrates an example cross-cohort encounter report 1895. The reports for each cohort may include summations of the RVUs for the different types of educational encounters, and may be mapped to the program competencies 1810 and compared and averaged to allow for evaluation of the curriculum over time. As illustrated in FIG. 18, the cross-cohort report 1895 may compare the program's curriculum from three cohorts (as illustrated in the left column) whose programs began from 2010 to 2012. This report 1895 may provide an ability look at the differences that curriculum changes made in the program during these years.

Cross-Academic Year Encounter Reports

FIG. 19 illustrates an example cross-academic year encounter report 1995. The reports for each academic year may include summations of the RVUs for the different types of educational encounters, and may be mapped to the program competencies 1910 and compared and averaged to allow for evaluation of the curriculum over time. As illustrated in FIG. 19, the report 1995 may compare the program's curriculum from 2013 to 2016 (as illustrated in the left column) during that time span. The curriculum report 1995 may illustrate an allocation of the various types of educational encounters for the entire curriculum with respect to the program competencies 1910, but without regard for the cohort. This report 1995 may provide the ability to look at the differences that specific instructors made in the program during these years.

FIG. 20 is a block diagram of an evaluation system 1600 according to some embodiments of the present invention. The evaluation system 1600 may use hardware, software implemented with hardware, firmware, tangible computer-readable storage media having instructions stored thereon and/or a combination thereof, and may be implemented in one or more computer systems or other processing systems. The evaluation system 1600 may also utilize a virtual instance of a computer. As such, the devices and methods described herein may be embodied in any combination of hardware and software.

As shown in FIG. 20, the evaluation system 1600 may include one or more processors 1610 and memory 1620 coupled to an interconnect 1630. The interconnect 1630 may be an abstraction that represents any one or more separate physical buses, point to point connections, or both connected by appropriate bridges, adapters, or controllers. The interconnect 1630, therefore, may include, for example, a system bus, a Peripheral Component Interconnect (PCI) bus or PCI-Express bus, a HyperTransport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB), IIC (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus, also called “Firewire.”

The processor(s) 1610 may be, or may include, one or more programmable general purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), trusted platform modules (TPMs), or a combination of such or similar devices, which may be collocated or distributed across one or more data networks. The processor 1610 may be configured to execute computer program instructions from the memory 1620 to perform some or all of the operations and methods for one or more of the embodiments disclosed herein.

The evaluation system 1600 may also include one or more communication adapters 1640 that may communicate with other communication devices and/or one or more networks, including any conventional, public and/or private, real and/or virtual, wired and/or wireless network, including the Internet. The communication adapters 1640 may include a communication interface and may be used to transfer information in the form of signals between the evaluation system 1600 and another computer system or a network (e.g., the Internet). The communication adapters 1640 may include a modem, a network interface (such as an Ethernet card), a wireless interface, a radio interface, a communications port, a PCMCIA slot and card, or the like. These components may be conventional components, such as those used in many conventional computing devices, and their functionality, with respect to conventional operations, is generally known to those skilled in the art.

The evaluation system 1600 may further include memory 1620 which may contain program code 1670 configured to execute operations associated with the methods described herein. The memory 1620 may include removable and/or fixed non-volatile memory devices (such as but not limited to a hard disk drive, flash memory, and/or like devices that may store computer program instructions and data on computer-readable media), volatile memory devices (such as but not limited to random access memory), as well as virtual storage (such as but not limited to a RAM disk). The memory 1620 may also include systems and/or devices used for storage of the evaluation system 1600.

The evaluation system 1600 may also include on or more input device(s) 1660 such as, but not limited to, a mouse, keyboard, camera, and/or a microphone. The input device(s) 1660 may be accessible to the one or more processors 1610 via the system interconnect 1630 and may be operated by the program code 1670 resident in the memory 1620

The evaluation system 1600 may also include a display 1690 capable of generating a display image, graphical user interface, and/or visual alert. The display 1690 may provide graphical user interfaces for receiving input, displaying intermediate operations/data, and/or exporting output of the methods described herein.

The evaluation system 1600 may also include a storage repository 1650. The storage repository may be accessible to the processor 1610 via the system interconnect 1630 and may additionally store information associated with the evaluation system 1600. For example, in some embodiments, the storage repository 1650 may contain accumulated applicant data, historical outcomes, and/or predictor model data as described herein.

The foregoing is illustrative of the present invention and is not to be construed as limiting thereof. Although a few exemplary embodiments of this invention have been described, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this invention. Accordingly, all such modifications are intended to be included within the scope of this invention as defined in the claims. In the claims, means-plus-function clauses, where used, are intended to cover the structures described herein as performing the recited function and not only structural equivalents but also equivalent structures. Therefore, it is to be understood that the foregoing is illustrative of the present invention and is not to be construed as limited to the specific embodiments disclosed, and that modifications to the disclosed embodiments, as well as other embodiments, are intended to be included within the scope of the appended claims. The invention is defined by the following claims, with equivalents of the claims to be included therein. 

1. (canceled)
 2. An electronic system comprising: a processor; a display coupled to the processor; and a memory coupled to the processor and storing computer readable program code that when executed by the processor causes the processor to perform operations comprising: for each instructor of a plurality of instructors, calculating a relative value unit (RVU) score for the instructor for each of a plurality of unique microcompetency codes that are associated with a respective instruction activity performed by the instructor; generating a normalized score for each instructor based on the calculated RVU score for each of the plurality of unique microcompetency codes; and displaying, via a graphical interface on the display, the normalized score for at least one of the plurality of instructors.
 3. The electronic system of claim 2, wherein the RVU score is at least partially based on a pre-defined assessment of difficulty and an estimated time for a student to complete a task associated with the instruction activity.
 4. The electronic system of claim 2, wherein the operations further comprise: automatically generating accreditation data comprising the normalized score for each instructor of the plurality of instructors for each of the unique microcompetency codes; and providing the accreditation data as part of an accreditation process for an educational institution associated with the plurality of instructors.
 5. The electronic system of claim 2, wherein at least one of the RVU scores is a time-normalized score based on a type of the instruction activity, and wherein the type of the instruction activity comprises at least one of didactic instruction, online instruction, seminar instruction, laboratory instruction, simulation instruction, and/or practical experience instruction.
 6. The electronic system of claim 5, wherein the RVU scores include RVU scores for each of didactic instruction, online instruction, seminar instruction, laboratory instruction, simulation instruction and practical experience instruction, and wherein the didactic instruction comprises one or more encounters in which the instructor communicates directly to a plurality of students.
 7. The electronic system of claim 6, wherein the online instruction comprises one or more encounters in which a computer is a mechanism for delivery of content to a plurality of students, wherein the seminar instruction comprises one or more encounters in which the seminar instruction guides discussions between one or more experts and the plurality of students, wherein the laboratory instruction comprises one or more encounters that places a student of the plurality of students into a role of performing one or more tasks of a skill that augment an understanding of didactic knowledge of the skill, and wherein the simulation instruction comprises one or more encounters that places the student of the plurality of students into a role of performing one or more tasks of a skill that simulates work and/or tasks performed by those experienced in the skill.
 8. The electronic system of claim 6, wherein the practical experience instruction comprises one or more encounters in which a student performs one or more tasks of a skill on a human patient under conditions corresponding to conditions experienced by those employed to perform the skill.
 9. The electronic system of claim 2, wherein the normalized score for the at least one of the plurality of instructors comprises a normalized listing that provides a relative participation in instruction for each of the plurality of unique microcompetency codes by the at least one of the plurality of instructors.
 10. A method comprising: for each instructor of a plurality of instructors, calculating a relative value unit (RVU) score for the instructor for each of a plurality of unique microcompetency codes that are associated with a respective instruction activity performed by the instructor; generating a normalized score for each instructor based on the calculated RVU score for each of the plurality of unique microcompetency codes; and displaying, via a graphical interface on the display, the normalized score for at least one of the plurality of instructors.
 11. The method of claim 10, wherein the RVU score is at least partially based on a pre-defined assessment of difficulty and an estimated time for a student to complete a task associated with the instruction activity.
 12. The method of claim 10, further comprising: automatically generating accreditation data comprising the normalized score for each instructor of the plurality of instructors for each of the unique microcompetency codes; and providing the accreditation data as part of an accreditation process for an educational institution associated with the plurality of instructors.
 13. The method of claim 10, wherein the normalized score for the at least one of the plurality of instructors comprises a normalized listing that provides a relative participation in instruction for each of the plurality of unique microcompetency codes by the at least one of the plurality of instructors.
 14. The method of claim 10, wherein at least one of the RVU scores is a time-normalized score based on a type of the instruction activity, and wherein the type of the instruction activity comprises at least one of didactic instruction, online instruction, seminar instruction, laboratory instruction, simulation instruction, and/or practical experience instruction.
 15. The method of claim 14, wherein the type of the instruction activity is the practical experience instruction, and wherein the method further comprises: generating a respective quantitative assessment of a performance of a student of the instructor for each of the unique microcompetency codes associated with the practical experience instruction; and adjusting the RVU score for each of the unique microcompetency codes based on the respective quantitative assessment for that unique microcompetency code.
 16. A computer program product for operating an electronic device comprising a non-transitory computer readable storage medium having computer readable program code embodied in the medium that when executed by a processor causes the processor to perform operations comprising: for each instructor of a plurality of instructors, calculating a relative value unit (RVU) score for the instructor for each of a plurality of unique microcompetency codes that are associated with a respective instruction activity performed by the instructor; generating a normalized score for each instructor based on the calculated RVU score for each of the plurality of unique microcompetency codes; and displaying, via a graphical interface on the display, the normalized score for at least one of the plurality of instructors.
 17. The computer program product of claim 16, wherein each of the plurality of unique microcompetency codes comprises a first topic code and a first sub-topic code dependent on the first topic code.
 18. The computer program product of claim 16, wherein the RVU score is at least partially based on a pre-defined assessment of difficulty and an estimated time for a student to complete a task associated with the instruction activity.
 19. The computer program product of claim 16, wherein the operations further comprise: automatically generating accreditation data comprising the normalized score for each instructor of the plurality of instructors for each of the unique microcompetency codes; and providing the accreditation data as part of an accreditation process for an educational institution associated with the plurality of instructors.
 20. The computer program product of claim 16, wherein the normalized score for the at least one of the plurality of instructors comprises a normalized listing that provides a relative participation in instruction for each of the plurality of unique microcompetency codes by the at least one of the plurality of instructors.
 21. The computer program product of claim 16, wherein at least one of the RVU scores is a time-normalized score based on a type of the instruction activity, and wherein the type of the instruction activity comprises at least one of didactic instruction, online instruction, seminar instruction, laboratory instruction, simulation instruction, and/or practical experience instruction. 